home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Networker 4.2.9
/
Networker 4.2.9 for IRIX 6.2, 6.3 and 6.4.img
/
relnotes
/
networker
/
ch3.z
/
ch3
Wrap
Text File
|
1997-07-08
|
11KB
|
331 lines
- 1 -
3. _C_h_a_n_g_e_s__a_n_d__A_d_d_i_t_i_o_n_s
Compared to IRIX NetWorker release 4.2.5, IRIX NetWorker
4.2.9 has the following features:
+o Improved throughput for local saves with PowerEdition
technology.
+o The jbm_enabler (jbconfig) command is improved to
simplify the installation of jukeboxes. In most cases,
jukeboxes are automatically detected, and only a
confirmation is required. (The original behavior is
still available by invoking with -noauto on the command
line.)
+o The DMO option has been revised. DMO version 2 provides
even faster backup of live Oracle databases.
+o The DBMI option is now available, to back up Informix
databases. Please see the documentation associated
with DBMI for full installation and operation
instructions. The following checklist will be helpful
in working with DBMI.
+o The Informix revision level must be ODS 7.21 or
above. That is, it must have OnBar, or must have
the OnBar binary in $INFORMIXDIR/bin.
+o The Informix database must be working correctly.
Check to make sure that ROOTSIZE is big enough.
+o Make sure the nsrdbmi script is appropriate for
your installation. You can make changes to the
copy of the nsrdbmi script in /usr/etc/nsrdbmi
while still retaining the original version in
/etc/nsrdbmi.sh. You may need to change the $PATH
variable in nsrdbmi, depending on your
installation.
+o Execute the following commands to inform the OnBar
executable of nwbsa.
echo "1|1.0.1|nwbsa|1" >>
$INFORMIXDIR/etc/sm_versions
dbaccess sysutils - <<EOF
load from '$INFORMIXDIR/etc/sm_versions'
insert into bar_version;
EOF
+o Make sure that you have the proper license for
DBMI installed in your license.dat file.
- 2 -
+o Make sure that savesetname is set correctly. When
nsrdbmi executes with the verbose option, all the
INFORMIX variables should be set correctly. This
should be set in the Client setup of nwadmin, and
is documented in the manual.
+o Make sure that nsrdbmi is configured as the backup
command for the client.
Compared to IRIX NetWorker release 4.1.3, IRIX NetWorker
release 4.2.5 had the following features:
+o Improved throughput is achieved by reducing NetWorker
CPU utilization.
+o The DMO option allows the Database Module for Oracle to
back up an Oracle database without taking it off-line.
+o When using the XFS filesystem, files greater than 2 GB
can be backed up and restored.
+o FLEXlm licensing is used in place of NetLS. Generally,
the licensing procedure is vary similar to that used in
previous versions. However, with FLEXlm, the license
strings are to be added to /var/flexlm/license.dat
instead of the license file used formerly.
+o The daemonlog file is now called daemon.log, and
entries are given timestamps.
+o The nsrjb command's output has changed slightly, and
you'll want to note this if you have scripts that
expect the older version's output. For instance, the
output from
#### nnnnssssrrrrjjjjbbbb ----CCCC ----vvvv ----jjjj OOOOddddeeeettttiiiiccccssss >>>>////ttttmmmmpppp////FFFF
formerly would state 'recycleable' in the last column
if the tape was recycleable. Now, since there is a
header 'recyclable' for the column, the last column is
simply 'yes' or 'no'.
+o Built-in support for rawasm is now included. This ASM
is intended for use in backing up raw disk partitions.
This functionality is now part of uasm, and is
documented on the uasm man page.
+o The saveindex command is replaced by savegrp -O.
- 3 -
+o The nsrck(1M) command is now documented in a man page.
+o A new -A annotation option for Archive is documented in
the nsrretrieve man page.
+o A sparse file is one which is stored on disk as a file
of a certain size, but which does not have as many disk
blocks allocated for it as would be indicated by its
overall size in bytes. Sparse files are created by
applications to access data stored in specific areas of
a file, without requiring disk space to be allocated
for unused areas.
With intelligent sparse file support, IRIX NetWorker
stores only the data actually allocated in a file. This
results in a quicker backup of the file, since the
unused data (zeros) is not sent across the network, nor
recorded to tape. In addition, when a sparse file is
recovered, it is recovered in the original sparse
organization, which saves disk space. We have worked
closely with Legato in the design of this feature to
ensure cross-platform tape format compatibility.
This feature is always turned on in IRIX NetWorker
4.2.x, and cannot be turned off.
+o IRIX NetWorker has traditionally offered large index
support, and this capabililty is extended further in
NetWorker 4.2.x. The size limit for a single client
index has been raised from 4G to 16G. (This feature is
part of IRIX NetWorker's PerformancePak.)
Sites must evaluate the performance implications of
large indexes before making the decision to allow
indexes to grow beyond 4 GB. Specifically, recovery
time of the IRIX NetWorker 4.2.x server may be
unacceptably long when using very large indexes, or
many somewhat large indexes. (More information about
this can be found in Chapter 5.)
+o NetWorker has always performed backups of multiple
filesystems in parallel, which is a primary reason for
NetWorker's excellent performance in the Enterprise
environment. Now, with IRIX NetWorker 4.2.x, the system
administrator can specify the number of parallel
streams to be devoted to a single filesystem. This can
increase NetWorker's overall performance, and is
especially valuable in the case of small backup
windows.
- 4 -
To use Multistream, specify your filesystem (in the
client setup window of nnnnwwwwaaaaddddmmmmiiiinnnn) with [n] in front of
it. The n stands for the number of parallelisms that
you want NetWorker to devote to the single filesystem
you specify.
For instance, you previously used "/h" to back up the
filesystem mounted at /h. To invoke Multistream, using
4 parallelisms, you would specify instead "[4]/h". Note
that you may also want to set sessions-per-device to 1,
which would force NetWorker to put each save stream
onto a separate tape drive. (The system administrator
should experiment with various values for the
Multistream value, the number of parallelisms, and
sessions-per-device, to arrive at the values which
result in optimum performance at a particular site.
Multistream is part of IRIX NetWorker's PerformancePak.
+o Support for backup of Macintoshr, Windows 95r, and
Windows NTr computer systems.
+o Support for more types of tape drives. You now have
more flexibility in both buying stand-alone tape drives
and purchasing jukeboxes that use particular types of
tape drives. In addition, IRIX NetWorker's
PerformancePak option allows use of exceptionally
high-performance tape drives.
Support for the following tape drives is new with this
release:
+o IBM 3590
+o Quantum DLT2000XT
+o Quantum DLT4000
+o Support for more types of jukeboxes. IRIX NetWorker
supports tape jukeboxes and tape formats which span the
range from the 6-slot 1-drive HP-C1553A 4mm unit to the
264-slot 3-drive ATL/Odetics 2640 DLT unit. You must
purchase a separate jukebox license for each jukebox
that you want to use with IRIX NetWorker.
Support for the following jukeboxes is new with this
release:
+o IBM 3590 ACF
- 5 -
+o Quantum DLT2500XT
+o Quantum DLT2700XT
+o Quantum DLT4500
+o STK 9710
+o STK 9714 (With jbm_enabler, choose "9710" to
enable the 9714.)
There are also some caveats:
+o DLT2000 drives in all peripherals used by NetWorker for
IRIX must have SGI personalities (firmware).
+o DLT2700 robotics used by NetWorker for IRIX must have
SGI personalities (firmware).
+o DLT4000 drives and DLT4700 robotics will not work
unless appropriate patches are applied changes are made
to certain system files. Some may not work even wwwwiiiitttthhhh
these changes. Please contact SGI Technical Assistance
Center (TAC) for patch information. See Chapter 5 of
these release notes for more help.
+o The internal firmware in an EXB-10i jukebox has a bug
that causes it to not respond correctly after the front
door to the jukebox has been opened and closed. See
Chapter 5 of the release notes for more information.